<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
    <title>Help - The Edit Sprint Backlog Page</title>
    <link rel="stylesheet" href="Style.css" />
</head>

<body>
    <a href="Default_help.htm">
    <img border="0" src="../Images/Banner2_Web.png" />
    </a>
    <br /><br />
    
    <p class="header1">Edit Sprint Backlog Table</p>
    <p>This page allows you to edit the features and tasks in a sprint's backlog.</p>
    <hr />
    
    <p class="header2">Table Display Options</p>
    <img src="images/edit_sprint_1.jpg" />
    
        <ul type="circle">
        <li><font class="header3">Sprint</font> - This dropdown includes a list of all the sprint backlogs that can be viewed on this page.</li>
        <li><font class="header3">Filter</font> - This dropdown includes a list of all the products and features who have tasks assigned during the selected sprint. The user can select to view an individual feature or all features at once.</li>
        <li><font class="header3">Owner</font> - This dropdown includes the aliases of all users who have tasks assigned during the selected sprint. The user can select to view the tasks for a single user or all users at once.</li>
        <li><font class="header3">Add Backlog Item</font> - This button allows the user to add items from the master backlog to the sprint backlog. It's use is described below in the "Adding a Backlog Item" section.</li>
        </ul>
        
    <hr />
    
    <p class="header2">Column Descriptions</p>
    <img src="images/edit_sprint_2.jpg" />
        
        <br /><br /><font class="note">Note: All underlined columns can be sorted on by clicking the column name. The sorting will occur within the current feature.</font>
        
        <ul type="circle">
       <li><font class="header3">Task</font> - This column includes the name of a task related to the product and feature listed at the top of the table.</li>
        <li><font class="header3">Owner</font> - This column includes the alias of the person responsible for completing the task.</li>
        <li><font class="header3">Base</font> - This column includes a numeric value indicating the number of hours/days initially estimated for completion of the task.</li>
        <li><font class="header3">Actual</font> - This column includes a numeric value indicating the number of hours/days that have currently been spent working on this task.</li>
        <li><font class="header3">Remaining</font> - This column includes a numeric value indicating the estimated number of hours/days remaining in order to complete the task.</li>
        <li><font class="header3">Punted</font> - This column includes a numeric value indicating the estimated number of hours/days remaining in order to complete the task.  These hours/days, however will not fit in the current sprint and should be completed in a later sprint.</li>
        <li><font class="header3">Unbuffered</font> - This column includes a checkbox allowing the user to indicate whether or not the owner's buffer is applied to the hours/days associated with this task. If the box is checked the buffer is not applied.</li>
        <li><font class="header3">Discovered</font> - This column includes a checkbox allowing the user to indicate whether the task was planned before the start of the sprint or if it was discovered during the course of the sprint. If the box is checked the task was discovered during the sprint.</li>
        <li><font class="header3">Priority</font> - This column includes a numeric value indicating the priority of completing this task without regard to other tasks. In general, it is used to show dependancies between tasks. For example, priority one tasks should be completed before priority two tasks.</li>
        <li><font class="header3">Notes</font> - This column includes notes associated with the task. These notes can be in regard to anything that the user wishes to track with the task.</li>
        </ul>
        
    <hr />
    
    <p class="header2">Adding a Backlog Item</p>
    <img src="images/edit_sprint_3.jpg" />
    
    <ul> 
        <li>Click the "Add Backlog Item" button at the top of the page.</li>
        <li>A new table titled "Add Master Backlog Items to Sprint" will appear with the following columns:
            <ul>
            <li><font class="header3">Product</font> - The column includes the name of the product this task is associated with.</li>
            <li><font class="header3">Feature</font> - This column includes the name of the feature that this task is associated with.</li>
            <li><font class="header3">Activity</font> - This column indicates the type of work this item requires, for example development, testing or documentation.</li>
            <li><font class="header3">Description</font> - This column includes the description of the task. </li>
            <li><font class="header3">Hours/Days</font> - This column includes the number of hours/days it is expected to take to complete this task.</li>
            </ul>
        </li>
        <li>Check the checkboxes for the items which should be added to the sprint backlog.</li>
        <li>Click "Add Selected Items" to add the items to the sprint backlog, or click "Cancel" to add none of the items.</li>
        <li>The items will now be listed in the "Edit Sprint Backlog" table, which will reappear.</li>
    </ul>
    
    <hr />
    
    <p class="header2">Adding a Task</p>
    <img src="images/edit_sprint_4.jpg" />
    
    <ul> 
        <ol> 
        <li>Click the "New Task" link on the bottom of the table for the feature which the task relates to.</li>
        <li>A new row with the default name of "Task Description" will appear in the table.</li>
        <li>Enter the data in the columns, according to their descriptions below:
            <ul type="circle">
            <li><font class="header3">Task</font> - Enter the name of a task related to the feature listed at the top of the table.</li>
            <li><font class="header3">Owner</font> - Enter the alias of the person responsible for completing the task.</li>
            <li><font class="header3">Base</font> - Enter a numeric value indicating the number of hours/days initially estimated for completion of the task.</li>
            <li><font class="header3">Actual</font> - Enter a numeric value indicating the number of hours/days that have currently been spent working on this task.</li>
            <li><font class="header3">Remaining</font> - Enter a numeric value indicating the estimated number of hours/days remaining in order to complete the task.</li>
            <li><font class="header3">Punted</font> - Enter a numeric value indicating the estimated number of hours/days remaining in order to complete the task.  These hours, however will not fit in the current sprint and should be completed in a later sprint.</li>
            <li><font class="header3">Unbuffered</font> - Select whether or not the owner's buffer is applied to the hours/days associated with this task. If the box is checked the buffer is not applied.</li>
            <li><font class="header3">Discovered</font> - Select whether the task was planned before the start of the sprint or if it was discovered during the course of the sprint. If the box is checked the task was discovered during the sprint.</li>
            <li><font class="header3">Priority</font> - Enter the priority of completing this task without regard to other tasks. In general, this value is used like the priority field in Product Studio. For example priority one tasks must be completed this sprint, while priority two tasks can wait longer.</li>
            <li><font class="header3">Notes</font> - Enter any notes associated with the task. These notes can be in regard to anything that the user wishes to track with the task.</li>
            </ul>
        </li>
        <li>Click "Update" to change the values for the row in the database, or click "Cancel" to discard the changes.</li>
        </ol>
    </ul>
    
    <hr />
    
    <p class="header2">Editing a Task</p>
    <img src="images/edit_sprint_4.jpg" />
    
       <ol> 
        <li>Click "Edit" in the row of the table you wish to edit.</li>
        <li>Edit the data in the columns, according to their descriptions below:
            <ul type="circle">
            <li><font class="header3">Task</font> - Enter the name of a task related to the feature listed at the top of the table.</li>
            <li><font class="header3">Owner</font> - Enter the alias of the person responsible for completing the task.</li>
            <li><font class="header3">Base</font> - Enter a numeric value indicating the number of hours/days initially estimated for completion of the task.</li>
            <li><font class="header3">Actual</font> - Enter a numeric value indicating the number of hours/days that have currently been spent working on this task.</li>
            <li><font class="header3">Remaining</font> - Enter a numeric value indicating the estimated number of hours/days remaining in order to complete the task.</li>
            <li><font class="header3">Punted</font> - Enter a numeric value indicating the estimated number of hours/days remaining in order to complete the task.  These hours, however will not fit in the current sprint and should be completed in a later sprint.</li>
            <li><font class="header3">Unbuffered</font> - Select whether or not the owner's buffer is applied to the hours/days associated with this task. If the box is checked the buffer is not applied.</li>
            <li><font class="header3">Discovered</font> - Select whether the task was planned before the start of the sprint or if it was discovered during the course of the sprint. If the box is checked the task was discovered during the sprint.</li>
            <li><font class="header3">Priority</font> - Enter the priority of completing this task without regard to other tasks. In general, this value is used like the priority field in Product Studio. For example priority one tasks must be completed this sprint, while priority two tasks can wait longer.</li>
            <li><font class="header3">Notes</font> - Enter any notes associated with the task. These notes can be in regard to anything that the user wishes to track with the task.</li>
            </ul>
        </li>
        <li>Click "Update" to change the values for the row in the database, or click "Cancel" to discard the changes.</li>
        </ol>
     <hr />
     
     <p class="header2">Copying a Task</p>
     <img src="images/edit_sprint_5.jpg" />
       <ol> 
        <li>Click "Copy" in the row of the table you wish to copy.</li>
        <li>A new entry will be created in the table with duplicate values.</li>
        <li>Edit the data in the columns, according to their descriptions below:
            <ul type="circle">
            <li><font class="header3">Task</font> - Enter the name of a task related to the feature listed at the top of the table.</li>
            <li><font class="header3">Owner</font> - Enter the alias of the person responsible for completing the task.</li>
            <li><font class="header3">Base</font> - Enter a numeric value indicating the number of hours/days initially estimated for completion of the task.</li>
            <li><font class="header3">Actual</font> - Enter a numeric value indicating the number of hours/days that have currently been spent working on this task.</li>
            <li><font class="header3">Remaining</font> - Enter a numeric value indicating the estimated number of hours/days remaining in order to complete the task.</li>
            <li><font class="header3">Punted</font> - Enter a numeric value indicating the estimated number of hours/days remaining in order to complete the task.  These hours, however will not fit in the current sprint and should be completed in a later sprint.</li>
            <li><font class="header3">Unbuffered</font> - Select whether or not the owner's buffer is applied to the hours/days associated with this task. If the box is checked the buffer is not applied.</li>
            <li><font class="header3">Discovered</font> - Select whether the task was planned before the start of the sprint or if it was discovered during the course of the sprint. If the box is checked the task was discovered during the sprint.</li>
            <li><font class="header3">Priority</font> - Enter the priority of completing this task without regard to other tasks. In general, this value is used like the priority field in Product Studio. For example priority one tasks must be completed this sprint, while priority two tasks can wait longer.</li>
            <li><font class="header3">Notes</font> - Enter any notes associated with the task. These notes can be in regard to anything that the user wishes to track with the task.</li>
            </ul>
        </li>
         <li>Click "Update" to change the values for the row in the database, or click "Cancel" to discard the changes.</li>
       </ol>
       <hr />
       
     <p class="header2">Spliting a Task</p>
     <img src="images/edit_sprint_5.jpg" />
       <ol> 
        <li>Click "Split" in the row of the table you wish to split.</li>
        <li>A new entry will be created in the table with duplicate values, but the hours/days in both the original entry and the new entry will be cut in half.</li>
        <li>Edit the data in the columns, according to their descriptions below:
            <ul type="circle">
            <li><font class="header3">Task</font> - Enter the name of a task related to the feature listed at the top of the table.</li>
            <li><font class="header3">Owner</font> - Enter the alias of the person responsible for completing the task.</li>
            <li><font class="header3">Base</font> - Enter a numeric value indicating the number of hours/days initially estimated for completion of the task.</li>
            <li><font class="header3">Actual</font> - Enter a numeric value indicating the number of hours/days that have currently been spent working on this task.</li>
            <li><font class="header3">Remaining</font> - Enter a numeric value indicating the estimated number of hours/days remaining in order to complete the task.</li>
            <li><font class="header3">Punted</font> - Enter a numeric value indicating the estimated number of hours/days remaining in order to complete the task.  These hours, however will not fit in the current sprint and should be completed in a later sprint.</li>
            <li><font class="header3">Unbuffered</font> - Select whether or not the owner's buffer is applied to the hours/days associated with this task. If the box is checked the buffer is not applied.</li>
            <li><font class="header3">Discovered</font> - Select whether the task was planned before the start of the sprint or if it was discovered during the course of the sprint. If the box is checked the task was discovered during the sprint.</li>
            <li><font class="header3">Priority</font> - Enter the priority of completing this task without regard to other tasks. In general, this value is used like the priority field in Product Studio. For example priority one tasks must be completed this sprint, while priority two tasks can wait longer.</li>
            <li><font class="header3">Notes</font> - Enter any notes associated with the task. These notes can be in regard to anything that the user wishes to track with the task.</li>
            </ul>
        </li>
         <li>Click "Update" to change the values for the row in the database, or click "Cancel" to discard the changes.</li>
       </ol>
       <hr />
       
     <p class="header2">Moving a Task Between Features</p>
     <ul> 
        <li>Select the "Show Feature (Edit Mode)" checkbox at the bottom of the table.</li>
        <li>Click "Edit" in the row of the table you wish to edit.</li>
        <li>In the dropdown list of feature names, select the feature which the task should be assigned to.</li>
        <li>Click "Update" to change the values for the row in the database, or click "Cancel" to discard the changes.</li>
     </ul>
     
     <hr />
       
     <p class="header2">Punting a Task</p>
     <ul> 
        <li>Click the punt link in the row of the table for the task you wish to punt.</li>
        <li>Click "OK" in the dialog box that appears to punt the product, otherwise click "Cancel"</li>
        <li>After "OK" is clicked, if the task has been worked on during the current sprint and has any work remaining, it will be taged with (punted). The remaining time will be added to the punted time and it will be placed in the product backlog. If the task had no time completed during the current sprint, it will be deleted from the current sprint and added to the product backlog.</li>
     </ul>
     
     <p><b>Note:</b> When punting a task from the Edit Sprint Backlog page or via Complete Sprint, any task proceeded by the text 
     "(Punted)" will not be punted successfully. Tackle places the "(Punted)" text at the start of a task, after it is punted, 
     to indicate that the task has been punted from a previous sprint. All operations associated with punting a task 
     or punted time on a task will not act on any task containing this text. Please ensure if you need to punt a task, 
     it does not contain the "(Punted)" text in the task description.</p>
     
     <hr />
       
     <p class="header2">Deleting a Task</p>
     <ul> 
        <li>Click the delete link in the row of the table you wish to delete.</li>
        <li>Click "OK" in the dialog box that appears to delete the product, otherwise click "Cancel"</li>
     </ul>
</body>

</html>
